Unit Test Results

       15 files  ±0    3 030 suites  ±0   1h 45m 33s ⏱️ + 13m 41s
12 625 tests ±0  12 045 ✔️ ±0  580 💤 ±0  0 ❌ ±0 
79 371 runs  ±0  78 494 ✔️ ±0  877 💤 ±0  0 ❌ ±0 

Results for commit 70491a4. ± Comparison against base commit 4b024bd.

♻️ This comment has been updated with latest results.

Well, some of the serialization also uses Nim old case objects, I believe.

@tersec I just added switch("warningAsError", "CaseTransition:on") to config to make sure the compilation fails if that's the case. nim-serialization does not support case objects (yet). Json and toml serializers fail with the nim-ser error, I checked.

Only nim-json-serilizer has it defined but for a test that overloads a readValue case object.

Unless there is some case where the Nim compiler does not warn about CaseTransition and the nimbus test suite does not cover that case, it should be fine. Otherwise, it'll throw a runtime FieldDefect.